Nice, thanks :) do we have to adjust the other @input's in the menu, too?

I thought about that as well 🤝 but it works fine with even with @input 🤷‍♂️ . So I've decided to reduce amount of changes.

If you want - I can adjust all of them, just say

Yes, would be nice :)

@input is no longer listed in the events section of the style guide. so might stop working sometime in the future :)

https://nextcloud-vue-components.netlify.app/#/Components/NcActions

Please also have a look at the custom file extensions, in my prod instance the field only takes numbers

@Chartman123 I did more changes, but...

1. there are short answer question type that relies on event?.isComposing (used for Chineese/Japanese). Sorry, but I have no any idea how to combine this with update:modelValue, it seems like we still need @input for that
2. extension selection not works for me. It works fine for vue-select but not works for Nextcloud wrapper. Looks like a bug on nextcloud-libraries/nextcloud-vue side

feel free to push to my branch

1. it seems like we still need @input for that

Yes, I think so, too 👍🏻

I could fix the extension selection by adding a key to the NcActionInput. Please test it :) If it's working on your instance, too, you can squash the commits and rebase on main :)

/backport to stable5.3

wow, with key helped. But how it works? Was the problem caused by reusing of another component?

I've reverted changes in the QuestionShort.vue (see comment)

Copilot suggested that it might have come from and interfered with some other type value in the attrs passed to the component...